Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 592d349fb6c876c84a88ed32bc7791564f025f1c3304d0255f1d07914c5ce2e7

Tx prefix hash: 80539a38f4fecd59482815800d218e0775aaa24e7390c98c0f16f081e0b38e97
Tx public key: ac7cb70831317a2f2e59fca56dc0fa6098f9610ae9e14e84c787c0e365508ec6
Timestamp: 1635996078 Timestamp [UCT]: 2021-11-04 03:21:18 Age [y:d:h:m:s]: 03:026:17:30:29
Block: 366898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 797613 RingCT/type: yes/0
Extra: 01ac7cb70831317a2f2e59fca56dc0fa6098f9610ae9e14e84c787c0e365508ec602110000000b745f00f8000000000000000000

1 output(s) for total of 37.352099536000 dcy

stealth address amount amount idx
00: 7ac9ccca2c205da3618edcaea7042b4b5b8c9cf1c41be174a18d41da4a973c6a 37.352099536000 744630 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 366908, "vin": [ { "gen": { "height": 366898 } } ], "vout": [ { "amount": 37352099536, "target": { "key": "7ac9ccca2c205da3618edcaea7042b4b5b8c9cf1c41be174a18d41da4a973c6a" } } ], "extra": [ 1, 172, 124, 183, 8, 49, 49, 122, 47, 46, 89, 252, 165, 109, 192, 250, 96, 152, 249, 97, 10, 233, 225, 78, 132, 199, 135, 192, 227, 101, 80, 142, 198, 2, 17, 0, 0, 0, 11, 116, 95, 0, 248, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8