Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f72d53f40199b2bd1ffb41229482023d610cc419aa0f5d60d6191d5afa5d2722

Tx prefix hash: 5b90a1c6ed188543a75b385697d879a5cf7171d5a4a80468639cfb0c8f045c00
Tx public key: d5302a45af7e9e05abc826c425980becf80643e5dfeade18bc3f8c5d7ba7aaa7
Timestamp: 1726818364 Timestamp [UCT]: 2024-09-20 07:46:04 Age [y:d:h:m:s]: 00:191:18:41:58
Block: 1114084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136878 RingCT/type: yes/0
Extra: 01d5302a45af7e9e05abc826c425980becf80643e5dfeade18bc3f8c5d7ba7aaa702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e38b84c945ba603964e66f96fad71d8bbfdfea183fe8765bc225876e5aaff6bd 0.600000000000 1593881 of 15

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": 1114094, "vin": [ { "gen": { "height": 1114084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e38b84c945ba603964e66f96fad71d8bbfdfea183fe8765bc225876e5aaff6bd" } } ], "extra": [ 1, 213, 48, 42, 69, 175, 126, 158, 5, 171, 200, 38, 196, 37, 152, 11, 236, 248, 6, 67, 229, 223, 234, 222, 24, 188, 63, 140, 93, 123, 167, 170, 167, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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