Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 809100282495755472fe8208660778eae7cae114dae3101f045820344a36caa2

Tx prefix hash: e601ae5d6275a7feaa943c2c59c610c3fc26d49b1b7afaa51824acfe1b1a3899
Tx public key: e0e52a20486d0f1d8a2514ff95a7c39b8e8412ce052665c9f5ffed751040c436
Timestamp: 1735159169 Timestamp [UCT]: 2024-12-25 20:39:29 Age [y:d:h:m:s]: 00:090:09:00:09
Block: 1183124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64345 RingCT/type: yes/0
Extra: 01e0e52a20486d0f1d8a2514ff95a7c39b8e8412ce052665c9f5ffed751040c4360211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4806c8a4f394d56334d31d31c72e36210061c68b90d1c211935d40d7a87aa04b 0.600000000000 1669565 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": 1183134, "vin": [ { "gen": { "height": 1183124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4806c8a4f394d56334d31d31c72e36210061c68b90d1c211935d40d7a87aa04b" } } ], "extra": [ 1, 224, 229, 42, 32, 72, 109, 15, 29, 138, 37, 20, 255, 149, 167, 195, 155, 142, 132, 18, 206, 5, 38, 101, 201, 245, 255, 237, 117, 16, 64, 196, 54, 2, 17, 0, 0, 0, 4, 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