Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebc384f54eeba9c355c20835a34aa33f3c78622872c34e7c631892532ee150a3

Tx prefix hash: f4ad92f79e9e7dfd4991b1f2dbc536fbd8c65d4b02f295593d2938e5263656d4
Tx public key: 1f4e1a22809b873e17768393e6f526b6650c56f95ca43ec6fe6bcb4fec8e88ff
Timestamp: 1731305215 Timestamp [UCT]: 2024-11-11 06:06:55 Age [y:d:h:m:s]: 00:200:21:04:57
Block: 1151189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143437 RingCT/type: yes/0
Extra: 011f4e1a22809b873e17768393e6f526b6650c56f95ca43ec6fe6bcb4fec8e88ff021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1e43f8f6e838cc5fc4111fb787446d2177e5245795740fd1eec6e4f61f2f6f8 0.600000000000 1636674 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": 1151199, "vin": [ { "gen": { "height": 1151189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1e43f8f6e838cc5fc4111fb787446d2177e5245795740fd1eec6e4f61f2f6f8" } } ], "extra": [ 1, 31, 78, 26, 34, 128, 155, 135, 62, 23, 118, 131, 147, 230, 245, 38, 182, 101, 12, 86, 249, 92, 164, 62, 198, 254, 107, 203, 79, 236, 142, 136, 255, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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