Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f180d630ebe16117e76fa6780a8261aaed5e0b8a265dbbc45d9fa54ea202e8a2

Tx prefix hash: 355dbc73380d461e8ae9d446c0cd8f7968bb2cb6157dc1b3d8c7b959ac7b495d
Tx public key: 6e83550d8f86f3154fbbfd1fadc7ca473ab8b8be3852484b704f4e1a3094bc58
Timestamp: 1699485711 Timestamp [UCT]: 2023-11-08 23:21:51 Age [y:d:h:m:s]: 01:075:16:27:48
Block: 887486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315461 RingCT/type: yes/0
Extra: 016e83550d8f86f3154fbbfd1fadc7ca473ab8b8be3852484b704f4e1a3094bc5802110000000375e3f0e9000000000000000000

1 output(s) for total of 0.703704731000 dcy

stealth address amount amount idx
00: 338159d7974c27ed815adead17247ef7f4c705c61f0abbc8abf9b9039a481caa 0.703704731000 1343371 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": 887496, "vin": [ { "gen": { "height": 887486 } } ], "vout": [ { "amount": 703704731, "target": { "key": "338159d7974c27ed815adead17247ef7f4c705c61f0abbc8abf9b9039a481caa" } } ], "extra": [ 1, 110, 131, 85, 13, 143, 134, 243, 21, 79, 187, 253, 31, 173, 199, 202, 71, 58, 184, 184, 190, 56, 82, 72, 75, 112, 79, 78, 26, 48, 148, 188, 88, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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