Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1987ecdc1c612347ad30eca1df1e6431f3551b79570c01ffe010baff8054e1c9

Tx prefix hash: a1a1eb1f0b0f371ea4a716ad0b8bd28f849076fa7e5d2877510710479d4faf10
Tx public key: 8e43bdd37cc900f3f11f5405e34763f279f9b09327e6be7f286b7442e88fee3a
Timestamp: 1723286874 Timestamp [UCT]: 2024-08-10 10:47:54 Age [y:d:h:m:s]: 00:222:19:40:09
Block: 1084813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159134 RingCT/type: yes/0
Extra: 018e43bdd37cc900f3f11f5405e34763f279f9b09327e6be7f286b7442e88fee3a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6754e3191e0b6f7da6944bba2fcc41959de58e0d4e96a0279aa15209d3d18e0b 0.600000000000 1559220 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": 1084823, "vin": [ { "gen": { "height": 1084813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6754e3191e0b6f7da6944bba2fcc41959de58e0d4e96a0279aa15209d3d18e0b" } } ], "extra": [ 1, 142, 67, 189, 211, 124, 201, 0, 243, 241, 31, 84, 5, 227, 71, 99, 242, 121, 249, 176, 147, 39, 230, 190, 127, 40, 107, 116, 66, 232, 143, 238, 58, 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