Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35a5ea1dfd232d7ca3e98662e96953054006bfcb7bafed194afd9f1539ab4668

Tx prefix hash: d27f6ff255ecc361b1a67ca37e878c5c4f2c2183be2244a59210b34fbc95ca8a
Tx public key: 50569f8bec53a67f41e2155e76b8155bded455fc0011d4bba45f6b611202f51f
Timestamp: 1718289894 Timestamp [UCT]: 2024-06-13 14:44:54 Age [y:d:h:m:s]: 01:227:23:59:56
Block: 1043381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421437 RingCT/type: yes/0
Extra: 0150569f8bec53a67f41e2155e76b8155bded455fc0011d4bba45f6b611202f51f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf95de0bc684f73dc1a9a7ef11f7c8d8a21273e7935ea072a3d1783da08ee35d 0.600000000000 1512522 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": 1043391, "vin": [ { "gen": { "height": 1043381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf95de0bc684f73dc1a9a7ef11f7c8d8a21273e7935ea072a3d1783da08ee35d" } } ], "extra": [ 1, 80, 86, 159, 139, 236, 83, 166, 127, 65, 226, 21, 94, 118, 184, 21, 91, 222, 212, 85, 252, 0, 17, 212, 187, 164, 95, 107, 97, 18, 2, 245, 31, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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