Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 834ee87e17b7b59073df0a958867a82b7f76d3652e1bc93b5cb590b680ed8089

Tx prefix hash: eaa7ddf8c3a3cf6f9dd40f74842c35a0cedb0c15175f353464936f9ac5a3f66e
Tx public key: b2a150352ef7196ba15aac3f11fa456bc0669221f2d2c8e15427943e042ad1fe
Timestamp: 1736469303 Timestamp [UCT]: 2025-01-10 00:35:03 Age [y:d:h:m:s]: 00:077:21:07:27
Block: 1193961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55426 RingCT/type: yes/0
Extra: 01b2a150352ef7196ba15aac3f11fa456bc0669221f2d2c8e15427943e042ad1fe021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f857451ef72794ce42d5e943c2ae4507b41e2c68fdcf7bb58edc1e109f0c068 0.600000000000 1680526 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": 1193971, "vin": [ { "gen": { "height": 1193961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f857451ef72794ce42d5e943c2ae4507b41e2c68fdcf7bb58edc1e109f0c068" } } ], "extra": [ 1, 178, 161, 80, 53, 46, 247, 25, 107, 161, 90, 172, 63, 17, 250, 69, 107, 192, 102, 146, 33, 242, 210, 200, 225, 84, 39, 148, 62, 4, 42, 209, 254, 2, 17, 0, 0, 0, 5, 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