Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1aa41c6781586b4e6059de554e18db17b9a0e100b3fc8f6c85830926afa8791

Tx prefix hash: 6fc5f63f2c1d069bed7d3b5a74920b881314eeb6a72fd7e07d64cc08d9c2d1ad
Tx public key: 123861908993b4871be7374fe16e104034d608f0d470c4bf36fb95b33144a579
Timestamp: 1694288390 Timestamp [UCT]: 2023-09-09 19:39:50 Age [y:d:h:m:s]: 01:106:17:09:41
Block: 844573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337598 RingCT/type: yes/0
Extra: 01123861908993b4871be7374fe16e104034d608f0d470c4bf36fb95b33144a579021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.976290620000 dcy

stealth address amount amount idx
00: 8920986103c6528d8f5e61a6e350af0b4fe14e1961c2c86a6fd82187bb2c19e7 0.976290620000 1297891 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": 844583, "vin": [ { "gen": { "height": 844573 } } ], "vout": [ { "amount": 976290620, "target": { "key": "8920986103c6528d8f5e61a6e350af0b4fe14e1961c2c86a6fd82187bb2c19e7" } } ], "extra": [ 1, 18, 56, 97, 144, 137, 147, 180, 135, 27, 231, 55, 79, 225, 110, 16, 64, 52, 214, 8, 240, 212, 112, 196, 191, 54, 251, 149, 179, 49, 68, 165, 121, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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