Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10c0f1f268450a1b361c8b20638c8fe591701d624b89d4d0515b3b18ffbf83d0

Tx prefix hash: c177c855e780305c6f2275d04ed3b5b96207fae18134758570d90c2a37b83d9c
Tx public key: 28469a32489ce22342f93780fbcd9a8c1d003454df881fd6141f629d2628530e
Timestamp: 1710442095 Timestamp [UCT]: 2024-03-14 18:48:15 Age [y:d:h:m:s]: 01:035:05:02:51
Block: 978332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286157 RingCT/type: yes/0
Extra: 0128469a32489ce22342f93780fbcd9a8c1d003454df881fd6141f629d2628530e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b38f7e5ee5ad2b293235442ca6f78a1f06f8fbc5b9eaf95113aff9151f7c29e 0.600000000000 1438355 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": 978342, "vin": [ { "gen": { "height": 978332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b38f7e5ee5ad2b293235442ca6f78a1f06f8fbc5b9eaf95113aff9151f7c29e" } } ], "extra": [ 1, 40, 70, 154, 50, 72, 156, 226, 35, 66, 249, 55, 128, 251, 205, 154, 140, 29, 0, 52, 84, 223, 136, 31, 214, 20, 31, 98, 157, 38, 40, 83, 14, 2, 17, 0, 0, 0, 4, 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