Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb0a76a47e4c37afcb1a30fa6e93e43aeb75bd856404c001a01ec665e2a21482

Tx prefix hash: 361a2ee3b67838045676fb9b90136b57f1c6b536b7bd61d0d06af6d6176baea0
Tx public key: 73e0d18b565b972ea415b80bf18f96971ed66a1fd803b36dd4aaae161927c756
Timestamp: 1762646731 Timestamp [UCT]: 2025-11-09 00:05:31 Age [y:d:h:m:s]: 00:011:17:36:38
Block: 1407994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8395 RingCT/type: yes/0
Extra: 0173e0d18b565b972ea415b80bf18f96971ed66a1fd803b36dd4aaae161927c7560211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b71ea6eff396b6ac1c4908531b35bc155d9ccb461bb0d4961e4b9c4f641db1c3 0.600000000000 1896419 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": 1408004, "vin": [ { "gen": { "height": 1407994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b71ea6eff396b6ac1c4908531b35bc155d9ccb461bb0d4961e4b9c4f641db1c3" } } ], "extra": [ 1, 115, 224, 209, 139, 86, 91, 151, 46, 164, 21, 184, 11, 241, 143, 150, 151, 30, 214, 106, 31, 216, 3, 179, 109, 212, 170, 174, 22, 25, 39, 199, 86, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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