Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed83a9c26c97dc7c9a38afc1a3f6c1c02120a650635af468c318923bc8e1750d

Tx prefix hash: 7ca43db8283c6a89d461b18bbe2c20109796488f0bf3b88eceb4a2b4dda6bcb4
Tx public key: 5899fd13740de6e8f55457ae768f65f76f2108ef6b716aba2425e600c8f80a1b
Timestamp: 1728392604 Timestamp [UCT]: 2024-10-08 13:03:24 Age [y:d:h:m:s]: 01:036:22:34:35
Block: 1127133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284784 RingCT/type: yes/0
Extra: 015899fd13740de6e8f55457ae768f65f76f2108ef6b716aba2425e600c8f80a1b021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 500d8895d3c2b01f4788aa8901f77804b8c20ccb8c4878fb1e0fee7b7c14c74c 0.600000000000 1609932 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": 1127143, "vin": [ { "gen": { "height": 1127133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "500d8895d3c2b01f4788aa8901f77804b8c20ccb8c4878fb1e0fee7b7c14c74c" } } ], "extra": [ 1, 88, 153, 253, 19, 116, 13, 230, 232, 245, 84, 87, 174, 118, 143, 101, 247, 111, 33, 8, 239, 107, 113, 106, 186, 36, 37, 230, 0, 200, 248, 10, 27, 2, 17, 0, 0, 0, 2, 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