Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0e813fd5136ca58d9374de7480e2b6acd3adfedc4cc27b8fca6ec80a7e634d3

Tx prefix hash: 97fb9e18603cd3278ef11e11ad64b5845967e7680a26d41fda573581eae3a9aa
Tx public key: 0f6285d8ddf71cdf3b3a5c1e147ac48995dc561d2b04b3bcc46bdadce9604d5a
Timestamp: 1706439356 Timestamp [UCT]: 2024-01-28 10:55:56 Age [y:d:h:m:s]: 01:279:13:48:20
Block: 945106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458603 RingCT/type: yes/0
Extra: 010f6285d8ddf71cdf3b3a5c1e147ac48995dc561d2b04b3bcc46bdadce9604d5a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0246c38aee3bca788d0421ce85c6786751b302d599157133f17827e01ea6db6 0.600000000000 1403416 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": 945116, "vin": [ { "gen": { "height": 945106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0246c38aee3bca788d0421ce85c6786751b302d599157133f17827e01ea6db6" } } ], "extra": [ 1, 15, 98, 133, 216, 221, 247, 28, 223, 59, 58, 92, 30, 20, 122, 196, 137, 149, 220, 86, 29, 43, 4, 179, 188, 196, 107, 218, 220, 233, 96, 77, 90, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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