Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b20f605e03941721a712427afa2d5e532b881eba780961be1c16a06cc9c53c0

Tx prefix hash: c188a08aa0299d9785ff3a3b7970fac28b043cb5f0780f545bcc4a823c080a66
Tx public key: 9cdb54b2c6ccf915e1676809d1c14d7a264616b5bc0c03c711a4e3483b0d7ef0
Timestamp: 1698164633 Timestamp [UCT]: 2023-10-24 16:23:53 Age [y:d:h:m:s]: 01:211:17:50:52
Block: 876740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412376 RingCT/type: yes/0
Extra: 019cdb54b2c6ccf915e1676809d1c14d7a264616b5bc0c03c711a4e3483b0d7ef00211000000014b8f5122000000000000000000

1 output(s) for total of 0.763829532000 dcy

stealth address amount amount idx
00: 002c9939b2992481c019342045ed7496a9c7301e4d448ea04f37ac0753529e8e 0.763829532000 1332084 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": 876750, "vin": [ { "gen": { "height": 876740 } } ], "vout": [ { "amount": 763829532, "target": { "key": "002c9939b2992481c019342045ed7496a9c7301e4d448ea04f37ac0753529e8e" } } ], "extra": [ 1, 156, 219, 84, 178, 198, 204, 249, 21, 225, 103, 104, 9, 209, 193, 77, 122, 38, 70, 22, 181, 188, 12, 3, 199, 17, 164, 227, 72, 59, 13, 126, 240, 2, 17, 0, 0, 0, 1, 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