Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea6a6655aeb481d0fb4e031fe7a05c9033d74b84b626aae11a4e74ed9e236423

Tx prefix hash: 09377325170ea7aa00a0424e709b6c65a111f68fa0a503d170529ed6db045b6d
Tx public key: 7b2d476b145b951414686b6d01c82968969c72b9289f0310592807d442d768ae
Timestamp: 1701150344 Timestamp [UCT]: 2023-11-28 05:45:44 Age [y:d:h:m:s]: 01:344:15:05:40
Block: 901279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505178 RingCT/type: yes/0
Extra: 017b2d476b145b951414686b6d01c82968969c72b9289f0310592807d442d768ae0211000000014b8f5122000000000000000000

1 output(s) for total of 0.633415251000 dcy

stealth address amount amount idx
00: 438c1fdecb5cca58e35705ee3929826b9aefa2d8b2a60a0bfcdaecc1792af404 0.633415251000 1357822 of 0

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": 901289, "vin": [ { "gen": { "height": 901279 } } ], "vout": [ { "amount": 633415251, "target": { "key": "438c1fdecb5cca58e35705ee3929826b9aefa2d8b2a60a0bfcdaecc1792af404" } } ], "extra": [ 1, 123, 45, 71, 107, 20, 91, 149, 20, 20, 104, 107, 109, 1, 200, 41, 104, 150, 156, 114, 185, 40, 159, 3, 16, 89, 40, 7, 212, 66, 215, 104, 174, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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