Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c24c937d42127c8d3f6351c76cb48b82d8596121cdb1a2f2614880a78e5140d

Tx prefix hash: 61d55066be611c623cf854132a607d30d78c963d2a04b2920f967e223eea3891
Tx public key: 0c63017a759e2bcf97ae1e3392a81141e979d00e9f7dfca4c5ca1438ba96623b
Timestamp: 1648577863 Timestamp [UCT]: 2022-03-29 18:17:43 Age [y:d:h:m:s]: 03:054:09:02:43
Block: 469060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 819145 RingCT/type: yes/0
Extra: 010c63017a759e2bcf97ae1e3392a81141e979d00e9f7dfca4c5ca1438ba96623b0211000000014a0f5013000000000000000000

1 output(s) for total of 17.132066630000 dcy

stealth address amount amount idx
00: 4e618b45cb8ae6e02fdb200f5e975a64f2f6db44dbbb8d2a1a6e2d652ca1f8fa 17.132066630000 887906 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": 469070, "vin": [ { "gen": { "height": 469060 } } ], "vout": [ { "amount": 17132066630, "target": { "key": "4e618b45cb8ae6e02fdb200f5e975a64f2f6db44dbbb8d2a1a6e2d652ca1f8fa" } } ], "extra": [ 1, 12, 99, 1, 122, 117, 158, 43, 207, 151, 174, 30, 51, 146, 168, 17, 65, 233, 121, 208, 14, 159, 125, 252, 164, 197, 202, 20, 56, 186, 150, 98, 59, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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