Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afda21773b4631dd5683cc49dd1073a1edf10dc3dbc3889f425956fa02605af4

Tx prefix hash: 1f5453b7c325abb2cdc2ff112326be91efac4ed03fb6b73f599469355d712dbe
Tx public key: d2e69f6aa04ee08e23a2a63a326512c71db60fdb1f6bed6c30706960ae4e5e76
Timestamp: 1736727089 Timestamp [UCT]: 2025-01-13 00:11:29 Age [y:d:h:m:s]: 00:064:01:42:15
Block: 1196079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45587 RingCT/type: yes/0
Extra: 01d2e69f6aa04ee08e23a2a63a326512c71db60fdb1f6bed6c30706960ae4e5e760211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1deb4d4d846d8811e38a6d7ff7484049e8789e30623a25466ace67464c7da6f0 0.600000000000 1682676 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": 1196089, "vin": [ { "gen": { "height": 1196079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1deb4d4d846d8811e38a6d7ff7484049e8789e30623a25466ace67464c7da6f0" } } ], "extra": [ 1, 210, 230, 159, 106, 160, 78, 224, 142, 35, 162, 166, 58, 50, 101, 18, 199, 29, 182, 15, 219, 31, 107, 237, 108, 48, 112, 105, 96, 174, 78, 94, 118, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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