Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 425b9bd4af640d149da6fc1501dc7fb29185fd0f464af4ef252ce69ac9b5fc46

Tx prefix hash: f5d51e3f4c38f071ad8a6eec01e58018e3d4b8a1f0f1e52ff77b389740ca45dc
Tx public key: cbe5744b1ddc62e7f6e92e1369b6be04d38f3b8e9f578ca06add20226f3986a6
Timestamp: 1737373740 Timestamp [UCT]: 2025-01-20 11:49:00 Age [y:d:h:m:s]: 00:152:00:11:15
Block: 1201398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108340 RingCT/type: yes/0
Extra: 01cbe5744b1ddc62e7f6e92e1369b6be04d38f3b8e9f578ca06add20226f3986a60211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69a4217937a751b5c9e8a2ed765f5b0f30e6bea813237e52349faf774e6cb860 0.600000000000 1688049 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": 1201408, "vin": [ { "gen": { "height": 1201398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69a4217937a751b5c9e8a2ed765f5b0f30e6bea813237e52349faf774e6cb860" } } ], "extra": [ 1, 203, 229, 116, 75, 29, 220, 98, 231, 246, 233, 46, 19, 105, 182, 190, 4, 211, 143, 59, 142, 159, 87, 140, 160, 106, 221, 32, 34, 111, 57, 134, 166, 2, 17, 0, 0, 0, 1, 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