Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7ec10d05acbdf000d445d14436f80e4f142c77033e138bb54cf7d5fbdad1141

Tx prefix hash: 2bf77a3f3df905e269368a252b8e7e9bc32f4993a2684a8b80562fa8125f62fc
Tx public key: 64568a89fbc275d6fff8ab7e39754e2b756bd79ed2ff8a398460e61dccb4f8ee
Timestamp: 1711770149 Timestamp [UCT]: 2024-03-30 03:42:29 Age [y:d:h:m:s]: 01:009:09:47:22
Block: 989345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267659 RingCT/type: yes/0
Extra: 0164568a89fbc275d6fff8ab7e39754e2b756bd79ed2ff8a398460e61dccb4f8ee0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dcdb56e688dcf2ec260198e25e6ec6100bff32def3efd4218b0b818ed064f0b 0.600000000000 1449642 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": 989355, "vin": [ { "gen": { "height": 989345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dcdb56e688dcf2ec260198e25e6ec6100bff32def3efd4218b0b818ed064f0b" } } ], "extra": [ 1, 100, 86, 138, 137, 251, 194, 117, 214, 255, 248, 171, 126, 57, 117, 78, 43, 117, 107, 215, 158, 210, 255, 138, 57, 132, 96, 230, 29, 204, 180, 248, 238, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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