Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b98f3aaa3d44f6ab9a7b76e23ad970871fbbf7f566673948957ea20f57d46034

Tx prefix hash: 8de72e52a21a7e6e257b1c801961aa2cf4fd9e9f918015d5e6b56186deeb02e9
Tx public key: d0860a776ffdf85d85b88f51faa0bed80e1ef4e0ea68a06cbe9224ddfff3aaa8
Timestamp: 1648990272 Timestamp [UCT]: 2022-04-03 12:51:12 Age [y:d:h:m:s]: 02:265:10:37:54
Block: 472305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 709475 RingCT/type: yes/0
Extra: 01d0860a776ffdf85d85b88f51faa0bed80e1ef4e0ea68a06cbe9224ddfff3aaa80211000000014a0f5013000000000000000000

1 output(s) for total of 16.713127179000 dcy

stealth address amount amount idx
00: a23017e3a76dbc152efa750c0a6ef592fb80576b50397af16c407237db85f56a 16.713127179000 891827 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": 472315, "vin": [ { "gen": { "height": 472305 } } ], "vout": [ { "amount": 16713127179, "target": { "key": "a23017e3a76dbc152efa750c0a6ef592fb80576b50397af16c407237db85f56a" } } ], "extra": [ 1, 208, 134, 10, 119, 111, 253, 248, 93, 133, 184, 143, 81, 250, 160, 190, 216, 14, 30, 244, 224, 234, 104, 160, 108, 190, 146, 36, 221, 255, 243, 170, 168, 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