Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c59684f6b40b952c0eaa3d893820693bd545af44ff8cc803c3be223b012f2bdf

Tx prefix hash: 767c21a2feb48f3077d93a111d598144ceebb9711fd1307ec4bdaa88e6e1d2b1
Tx public key: fcdf1b014192c61f8c0e7661f958456b8445a6bb4a4ed9883a6fab5e3c8543ce
Timestamp: 1714324357 Timestamp [UCT]: 2024-04-28 17:12:37 Age [y:d:h:m:s]: 01:189:17:24:15
Block: 1010491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394243 RingCT/type: yes/0
Extra: 01fcdf1b014192c61f8c0e7661f958456b8445a6bb4a4ed9883a6fab5e3c8543ce02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c02d75c01ba156d6f56c0220b246a5ecff6cc9b693c72d6e615bade98d4e1184 0.600000000000 1472465 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": 1010501, "vin": [ { "gen": { "height": 1010491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c02d75c01ba156d6f56c0220b246a5ecff6cc9b693c72d6e615bade98d4e1184" } } ], "extra": [ 1, 252, 223, 27, 1, 65, 146, 198, 31, 140, 14, 118, 97, 249, 88, 69, 107, 132, 69, 166, 187, 74, 78, 217, 136, 58, 111, 171, 94, 60, 133, 67, 206, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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