Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d451630b633abafb99468bc2be265642a321e08ce552ccb12ef0c9b7aa1380a

Tx prefix hash: 0d7275e81568b56e87785f5a88f47966453fef18a474d8d0361100e57f3a5df4
Tx public key: b2f4e7cfa37ea85201ac05c5e5ded2b84f368cdbbc73ca48fde8cd30816fa7de
Timestamp: 1694312695 Timestamp [UCT]: 2023-09-10 02:24:55 Age [y:d:h:m:s]: 01:171:17:05:24
Block: 844778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383795 RingCT/type: yes/0
Extra: 01b2f4e7cfa37ea85201ac05c5e5ded2b84f368cdbbc73ca48fde8cd30816fa7de0211000000064b8f5122000000000000000000

1 output(s) for total of 0.974764864000 dcy

stealth address amount amount idx
00: 27cf5f2da3ab463eaaa864a7f0899fde693dbb9765a4c7f5e721191d4694ecf9 0.974764864000 1298108 of 0

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": 844788, "vin": [ { "gen": { "height": 844778 } } ], "vout": [ { "amount": 974764864, "target": { "key": "27cf5f2da3ab463eaaa864a7f0899fde693dbb9765a4c7f5e721191d4694ecf9" } } ], "extra": [ 1, 178, 244, 231, 207, 163, 126, 168, 82, 1, 172, 5, 197, 229, 222, 210, 184, 79, 54, 140, 219, 188, 115, 202, 72, 253, 232, 205, 48, 129, 111, 167, 222, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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