Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffbb6192a98b71a018ba3e57bc8958ee07ff49610fe8d639d9a948177b02a054

Tx prefix hash: 34aa483fd6049652c7788b8f275e0c40cf7a89d628d847f1c6f7c352665226f2
Tx public key: 4b5c230b17f262aa733d90b9eb2055dd1250d88e99daaa5ce22a3aaaa8aa46be
Timestamp: 1720967564 Timestamp [UCT]: 2024-07-14 14:32:44 Age [y:d:h:m:s]: 00:259:03:01:57
Block: 1065585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185110 RingCT/type: yes/0
Extra: 014b5c230b17f262aa733d90b9eb2055dd1250d88e99daaa5ce22a3aaaa8aa46be02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbd2ea8e558c48682524eb0f0f4e1ebfeb6e869db5149990f97201f3fa61c413 0.600000000000 1536134 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": 1065595, "vin": [ { "gen": { "height": 1065585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbd2ea8e558c48682524eb0f0f4e1ebfeb6e869db5149990f97201f3fa61c413" } } ], "extra": [ 1, 75, 92, 35, 11, 23, 242, 98, 170, 115, 61, 144, 185, 235, 32, 85, 221, 18, 80, 216, 142, 153, 218, 170, 92, 226, 42, 58, 170, 168, 170, 70, 190, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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