Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a305450ed79306294d5ba8c04ccb3df8864b3bf5d55b5005344df88deea72e01

Tx prefix hash: 04f1239823e97b18a117648f7893c0c96b8a3ed87cc9296ada6b946341f1931b
Tx public key: 9ec66ac540d3fd2c4d67ddffaaecdc8704726950cb744911b8f319a4037bfd35
Timestamp: 1699352985 Timestamp [UCT]: 2023-11-07 10:29:45 Age [y:d:h:m:s]: 01:146:16:45:10
Block: 886383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366023 RingCT/type: yes/0
Extra: 019ec66ac540d3fd2c4d67ddffaaecdc8704726950cb744911b8f319a4037bfd3502110000000575e3f0e9000000000000000000

1 output(s) for total of 0.709651572000 dcy

stealth address amount amount idx
00: 0e9f6f4796b90b575deeb40ea38528320cbbafc96a06719665c2a24db483e8d6 0.709651572000 1342198 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": 886393, "vin": [ { "gen": { "height": 886383 } } ], "vout": [ { "amount": 709651572, "target": { "key": "0e9f6f4796b90b575deeb40ea38528320cbbafc96a06719665c2a24db483e8d6" } } ], "extra": [ 1, 158, 198, 106, 197, 64, 211, 253, 44, 77, 103, 221, 255, 170, 236, 220, 135, 4, 114, 105, 80, 203, 116, 73, 17, 184, 243, 25, 164, 3, 123, 253, 53, 2, 17, 0, 0, 0, 5, 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