Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d89df732e68c482b4a4e114bfb262e23b65d3cd9624d657681935d106ce6b9e6

Tx prefix hash: 933a9aadbc868311cf3d2303e0550f0c3be826c3bfa5846c2113745e9b6ec80d
Tx public key: e4984a4f0b48f050b5aa1de697feeea83038735a76ce85032e463c3e30219e42
Timestamp: 1714120980 Timestamp [UCT]: 2024-04-26 08:43:00 Age [y:d:h:m:s]: 00:258:04:18:20
Block: 1008814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184798 RingCT/type: yes/0
Extra: 01e4984a4f0b48f050b5aa1de697feeea83038735a76ce85032e463c3e30219e4202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49dbaf06fc1b274446037921bfc49d205c3ca6bd8fff91582bd3aa7e2d8e0cda 0.600000000000 1470294 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": 1008824, "vin": [ { "gen": { "height": 1008814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49dbaf06fc1b274446037921bfc49d205c3ca6bd8fff91582bd3aa7e2d8e0cda" } } ], "extra": [ 1, 228, 152, 74, 79, 11, 72, 240, 80, 181, 170, 29, 230, 151, 254, 238, 168, 48, 56, 115, 90, 118, 206, 133, 3, 46, 70, 60, 62, 48, 33, 158, 66, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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