Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3aea1eeb951f4bb0b9c7dc2767f6673024100a670960ae3f2fad6956542ec54

Tx prefix hash: 6e74f95b7f6163d6bc270c5e2266383ac5711dfc4f97695a08b38b1bccc1f46d
Tx public key: 6c4dba63f878923e67f30b98986af4e89fe3daf87430cc74730d390d7eaa1b42
Timestamp: 1737563411 Timestamp [UCT]: 2025-01-22 16:30:11 Age [y:d:h:m:s]: 00:147:04:57:19
Block: 1202970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104940 RingCT/type: yes/0
Extra: 016c4dba63f878923e67f30b98986af4e89fe3daf87430cc74730d390d7eaa1b42021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50dda25fd88b5d19ac5f8f2f477825ccf7ade9e306fc63442842d5faf9f960d3 0.600000000000 1689639 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": 1202980, "vin": [ { "gen": { "height": 1202970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50dda25fd88b5d19ac5f8f2f477825ccf7ade9e306fc63442842d5faf9f960d3" } } ], "extra": [ 1, 108, 77, 186, 99, 248, 120, 146, 62, 103, 243, 11, 152, 152, 106, 244, 232, 159, 227, 218, 248, 116, 48, 204, 116, 115, 13, 57, 13, 126, 170, 27, 66, 2, 17, 0, 0, 0, 8, 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