Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62a01f543c7c211bb1c41854e32487bc43b26d0b7647a9773057fa11871e5efe

Tx prefix hash: a1d96fad2778e861925d4372b1301cc4699de080727a6f6bed9322b2d5a945a1
Tx public key: b03e49de40ff71c4e27d8a8d0f3ccc60c9b452aceb033cd53ba4bb9be4f7abf7
Timestamp: 1705468134 Timestamp [UCT]: 2024-01-17 05:08:54 Age [y:d:h:m:s]: 01:151:11:54:38
Block: 937047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369334 RingCT/type: yes/0
Extra: 01b03e49de40ff71c4e27d8a8d0f3ccc60c9b452aceb033cd53ba4bb9be4f7abf702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12481f80888a24424a9084077319e9c7f08e76ccb4ceae103bfcce92f53b3424 0.600000000000 1395091 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": 937057, "vin": [ { "gen": { "height": 937047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12481f80888a24424a9084077319e9c7f08e76ccb4ceae103bfcce92f53b3424" } } ], "extra": [ 1, 176, 62, 73, 222, 64, 255, 113, 196, 226, 125, 138, 141, 15, 60, 204, 96, 201, 180, 82, 172, 235, 3, 60, 213, 59, 164, 187, 155, 228, 247, 171, 247, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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