Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0734c75797b230bcbeb8f42ef4df6963faebad235c7ed7b75169b70d198c9769

Tx prefix hash: 941fcd3ebb654117ed449a4f80293abf21e1f21a269fbf62bd7183478478c201
Tx public key: 7a8c176f189417faa34ca4a037e38b24aab5444f9af87e7d96227bb56087e01d
Timestamp: 1636063792 Timestamp [UCT]: 2021-11-04 22:09:52 Age [y:d:h:m:s]: 03:130:17:07:20
Block: 367453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 871750 RingCT/type: yes/0
Extra: 017a8c176f189417faa34ca4a037e38b24aab5444f9af87e7d96227bb56087e01d02110000000f6a2c97e6000000000000000000

1 output(s) for total of 37.194912797000 dcy

stealth address amount amount idx
00: 9e0d9a5ca4f2c3fdddb32a21d3b4ca93a4a9f7f5471cf00910211ba3714d57d9 37.194912797000 745599 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": 367463, "vin": [ { "gen": { "height": 367453 } } ], "vout": [ { "amount": 37194912797, "target": { "key": "9e0d9a5ca4f2c3fdddb32a21d3b4ca93a4a9f7f5471cf00910211ba3714d57d9" } } ], "extra": [ 1, 122, 140, 23, 111, 24, 148, 23, 250, 163, 76, 164, 160, 55, 227, 139, 36, 170, 181, 68, 79, 154, 248, 126, 125, 150, 34, 123, 181, 96, 135, 224, 29, 2, 17, 0, 0, 0, 15, 106, 44, 151, 230, 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