Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea6af3cd907fee7a6cf7f52e58c437252265a0fba1249f79d860c9b7d77116c

Tx prefix hash: 897f712bf8acd8c8605521e69fddddcc13219439ef788b4f9fd9630e9309b437
Tx public key: c92db4f8582d517f65a56dad73b7cb9cd65e6baeb31f6ebfecbfcd94c97e683b
Timestamp: 1711832287 Timestamp [UCT]: 2024-03-30 20:58:07 Age [y:d:h:m:s]: 01:029:00:52:48
Block: 989856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281722 RingCT/type: yes/0
Extra: 01c92db4f8582d517f65a56dad73b7cb9cd65e6baeb31f6ebfecbfcd94c97e683b02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65b0b95a743c65f866bc82a71b03f15b8c63a5443536abac8d260be934ced13f 0.600000000000 1450174 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": 989866, "vin": [ { "gen": { "height": 989856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b0b95a743c65f866bc82a71b03f15b8c63a5443536abac8d260be934ced13f" } } ], "extra": [ 1, 201, 45, 180, 248, 88, 45, 81, 127, 101, 165, 109, 173, 115, 183, 203, 156, 214, 94, 107, 174, 179, 31, 110, 191, 236, 191, 205, 148, 201, 126, 104, 59, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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