Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a555f35a4e5c1b99163aff5f961dd6c03ce0cacb7c1e4bbaaa5ec09f541aeb6f

Tx prefix hash: edf91c51c25136395580901984135d73cba6a89b38cba5279d6d5433bb3d1594
Tx public key: 694b7050f0360d5157d4079c103070f7b6c49690afbcb5fc68f87582aae60b3f
Timestamp: 1704801909 Timestamp [UCT]: 2024-01-09 12:05:09 Age [y:d:h:m:s]: 01:082:18:30:51
Block: 931538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320261 RingCT/type: yes/0
Extra: 01694b7050f0360d5157d4079c103070f7b6c49690afbcb5fc68f87582aae60b3f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bec71a991d24aac4a2817d48802afdd7d4dacb4b250a30384de105395fee1bc1 0.600000000000 1389440 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": 931548, "vin": [ { "gen": { "height": 931538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bec71a991d24aac4a2817d48802afdd7d4dacb4b250a30384de105395fee1bc1" } } ], "extra": [ 1, 105, 75, 112, 80, 240, 54, 13, 81, 87, 212, 7, 156, 16, 48, 112, 247, 182, 196, 150, 144, 175, 188, 181, 252, 104, 248, 117, 130, 170, 230, 11, 63, 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