Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7571485c5a4ca283a952a1ce5c63fe3fc68d66df3170150cf554d61e0cf113ac

Tx prefix hash: 303388f6a3804e66ad18795e15d1213e947e5097d731d70b3eeccdfe50b1fafc
Tx public key: 2aa16055eb6a4b951fa821e8603fd7589c2cf355e2f6d68e31973809c50c9fe4
Timestamp: 1727214087 Timestamp [UCT]: 2024-09-24 21:41:27 Age [y:d:h:m:s]: 00:254:01:06:41
Block: 1117361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181424 RingCT/type: yes/0
Extra: 012aa16055eb6a4b951fa821e8603fd7589c2cf355e2f6d68e31973809c50c9fe402110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d87332611b1711454451731bdb1702d96dbacc16cdda2378894f6aa11af8d1a 0.600000000000 1598172 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": 1117371, "vin": [ { "gen": { "height": 1117361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d87332611b1711454451731bdb1702d96dbacc16cdda2378894f6aa11af8d1a" } } ], "extra": [ 1, 42, 161, 96, 85, 235, 106, 75, 149, 31, 168, 33, 232, 96, 63, 215, 88, 156, 44, 243, 85, 226, 246, 214, 142, 49, 151, 56, 9, 197, 12, 159, 228, 2, 17, 0, 0, 0, 12, 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