Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 290f4ee4b48fbaabe4d96cf9fbdaff3c8696298da60fb32d3f221d395acebc9f

Tx prefix hash: 46d9f45dd611ede1182a92f6ef3adc4abd6f53a8ad7e6191a0f4d5b7fbc6da5d
Tx public key: fd15432ad463ce9304965a8316ca68ae8a7e86dab401f5ad68c1a375b850e086
Timestamp: 1722111656 Timestamp [UCT]: 2024-07-27 20:20:56 Age [y:d:h:m:s]: 00:169:01:45:01
Block: 1075067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120957 RingCT/type: yes/0
Extra: 01fd15432ad463ce9304965a8316ca68ae8a7e86dab401f5ad68c1a375b850e08602110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39e2c4404039f60b54084556fd0fbd75d6c3d1a18107d2676502d9a8d4f73f73 0.600000000000 1547588 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": 1075077, "vin": [ { "gen": { "height": 1075067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39e2c4404039f60b54084556fd0fbd75d6c3d1a18107d2676502d9a8d4f73f73" } } ], "extra": [ 1, 253, 21, 67, 42, 212, 99, 206, 147, 4, 150, 90, 131, 22, 202, 104, 174, 138, 126, 134, 218, 180, 1, 245, 173, 104, 193, 163, 117, 184, 80, 224, 134, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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