Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17f0006104c73c2b1bc56a6e7f1b09175cb3a3ce318de84c95efb888174e5571

Tx prefix hash: 0fdcf9ae304df6d630324e0a784fd7d0ff16ecdfd689bd328612a041f21d7c76
Tx public key: 4a54067fd8df5601dc9cfdb2a271db575d871ce14a8c3b1560ba11ec1c150962
Timestamp: 1721634904 Timestamp [UCT]: 2024-07-22 07:55:04 Age [y:d:h:m:s]: 00:327:02:48:00
Block: 1071103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233682 RingCT/type: yes/0
Extra: 014a54067fd8df5601dc9cfdb2a271db575d871ce14a8c3b1560ba11ec1c15096202110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e87abae8feb74726c9615e0f5aba41093966a9f1c2a53d77658d63e56d1c34e 0.600000000000 1543206 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": 1071113, "vin": [ { "gen": { "height": 1071103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e87abae8feb74726c9615e0f5aba41093966a9f1c2a53d77658d63e56d1c34e" } } ], "extra": [ 1, 74, 84, 6, 127, 216, 223, 86, 1, 220, 156, 253, 178, 162, 113, 219, 87, 93, 135, 28, 225, 74, 140, 59, 21, 96, 186, 17, 236, 28, 21, 9, 98, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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