Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e195d9ce5a1dd387f2333467733e71cd0e8ce5c32e96989c949b1da01b1cb17

Tx prefix hash: 81f330de2337f74dc771494c3386a4d8119dc0b365deb4b1c741571dfdc47296
Tx public key: 656c9cced00c3bc13bfad39d7e38041ac3df78263e1537f8119b3d00a856bf15
Timestamp: 1728019017 Timestamp [UCT]: 2024-10-04 05:16:57 Age [y:d:h:m:s]: 00:161:07:21:12
Block: 1124041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115093 RingCT/type: yes/0
Extra: 01656c9cced00c3bc13bfad39d7e38041ac3df78263e1537f8119b3d00a856bf1502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21312adf8d9b7f40d5cb47ace2b4d4795d9b0ce815c056e2602d5af439aad0b2 0.600000000000 1606604 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": 1124051, "vin": [ { "gen": { "height": 1124041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21312adf8d9b7f40d5cb47ace2b4d4795d9b0ce815c056e2602d5af439aad0b2" } } ], "extra": [ 1, 101, 108, 156, 206, 208, 12, 59, 193, 59, 250, 211, 157, 126, 56, 4, 26, 195, 223, 120, 38, 62, 21, 55, 248, 17, 155, 61, 0, 168, 86, 191, 21, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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