Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13e9eb470dbd1f36d319ba45e6a370b08cef2b9f5bab4c9510ca2b444e31c84e

Tx prefix hash: 36a5fd2cc1fa2707cf37b7546de97b77ffe7fc0c75567017447e99b12feb84b0
Tx public key: 3f9679abf4cb6777caec2d1e1928e7273ea0e9605071b49086ef3d06ae0a4fbd
Timestamp: 1732646451 Timestamp [UCT]: 2024-11-26 18:40:51 Age [y:d:h:m:s]: 00:345:06:11:04
Block: 1162304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244271 RingCT/type: yes/0
Extra: 013f9679abf4cb6777caec2d1e1928e7273ea0e9605071b49086ef3d06ae0a4fbd021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac350c1bafaf4b592259ecdc6e54321f206a1b0bed7be607f00f06695dd76589 0.600000000000 1647959 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": 1162314, "vin": [ { "gen": { "height": 1162304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac350c1bafaf4b592259ecdc6e54321f206a1b0bed7be607f00f06695dd76589" } } ], "extra": [ 1, 63, 150, 121, 171, 244, 203, 103, 119, 202, 236, 45, 30, 25, 40, 231, 39, 62, 160, 233, 96, 80, 113, 180, 144, 134, 239, 61, 6, 174, 10, 79, 189, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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