Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68ea2555c944d371a8e7df7b373e4ca67c4c06f3d22c29e349f2b37450e86ba5

Tx prefix hash: 9dbf49784a77eb7ffe237f8193ed2f893ac4530ef8ea19bf0ce21055f1c9093c
Tx public key: 20592f6b7c8491d788e1f9e5704e8cc36346b870f8a07bcf6e0de8d392e39784
Timestamp: 1723552793 Timestamp [UCT]: 2024-08-13 12:39:53 Age [y:d:h:m:s]: 00:243:22:39:15
Block: 1087013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174236 RingCT/type: yes/0
Extra: 0120592f6b7c8491d788e1f9e5704e8cc36346b870f8a07bcf6e0de8d392e3978402110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1cb09652c6fd85a7899df950135aff067fa29701e2a1a70957f299e07990706 0.600000000000 1561614 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": 1087023, "vin": [ { "gen": { "height": 1087013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1cb09652c6fd85a7899df950135aff067fa29701e2a1a70957f299e07990706" } } ], "extra": [ 1, 32, 89, 47, 107, 124, 132, 145, 215, 136, 225, 249, 229, 112, 78, 140, 195, 99, 70, 184, 112, 248, 160, 123, 207, 110, 13, 232, 211, 146, 227, 151, 132, 2, 17, 0, 0, 0, 10, 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