Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c262e2c2f2bde5746461b5e72ba3ae606e44d66b6b29c627c0b561b0d221c5d7

Tx prefix hash: 6e3f4d36e1fa830f88ba167dad4f654ab74ea657e4aa15c8994b0855fa10912f
Tx public key: 45cde6e9298751c146b0b315f5416c732102a1bb46d7684ae0c8f40d1e2640cb
Timestamp: 1727779179 Timestamp [UCT]: 2024-10-01 10:39:39 Age [y:d:h:m:s]: 00:166:12:57:20
Block: 1122052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118832 RingCT/type: yes/0
Extra: 0145cde6e9298751c146b0b315f5416c732102a1bb46d7684ae0c8f40d1e2640cb02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 963d95858121ead094d01a4a634bd9864cbfbd4ec6caad5a6b6d92ae1647084a 0.600000000000 1604423 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": 1122062, "vin": [ { "gen": { "height": 1122052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "963d95858121ead094d01a4a634bd9864cbfbd4ec6caad5a6b6d92ae1647084a" } } ], "extra": [ 1, 69, 205, 230, 233, 41, 135, 81, 193, 70, 176, 179, 21, 245, 65, 108, 115, 33, 2, 161, 187, 70, 215, 104, 74, 224, 200, 244, 13, 30, 38, 64, 203, 2, 17, 0, 0, 0, 8, 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