Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b031720e080fc7f53d3ece61be35e58fcb8c608b9f5d6a550965a43c14ba94d

Tx prefix hash: 33583ebb731f1bd88a66a21a1e94dcf1392682531dab229d0e4d968ba3c93138
Tx public key: e420804aeea9868cbeefc1b52504ef69c26be346ec9b923f8a63c2895903e4e7
Timestamp: 1707801365 Timestamp [UCT]: 2024-02-13 05:16:05 Age [y:d:h:m:s]: 01:014:04:58:14
Block: 956422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271157 RingCT/type: yes/0
Extra: 01e420804aeea9868cbeefc1b52504ef69c26be346ec9b923f8a63c2895903e4e70211000000150011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ce0d17df629c426b8a743c65b2bc56ffacf0f938ec224cc58ae1f6ff7534be7 0.600000000000 1415730 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": 956432, "vin": [ { "gen": { "height": 956422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ce0d17df629c426b8a743c65b2bc56ffacf0f938ec224cc58ae1f6ff7534be7" } } ], "extra": [ 1, 228, 32, 128, 74, 238, 169, 134, 140, 190, 239, 193, 181, 37, 4, 239, 105, 194, 107, 227, 70, 236, 155, 146, 63, 138, 99, 194, 137, 89, 3, 228, 231, 2, 17, 0, 0, 0, 21, 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