Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23c293a872569e23dc63aced592247195052d6d10596b10357597567fafc54ec

Tx prefix hash: ddabcaa8a40cc9f149d81cac0ac7b0e7707b3fb71c7b3f2afdbb2808bc9bc1ee
Tx public key: b9fceea733b5a256d15c968a10981344c4ee2a2de9bf260a28ef804de69504bb
Timestamp: 1574749800 Timestamp [UCT]: 2019-11-26 06:30:00 Age [y:d:h:m:s]: 05:034:13:53:05
Block: 17698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167542 RingCT/type: yes/0
Extra: 01b9fceea733b5a256d15c968a10981344c4ee2a2de9bf260a28ef804de69504bb021100000001f95225a5000000000000000000

1 output(s) for total of 536.241053267000 dcy

stealth address amount amount idx
00: 356b8b07fd30d5cd6808ca623635707e1f744e921c57cfb26a955b3a2661e2f4 536.241053267000 26112 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": 17708, "vin": [ { "gen": { "height": 17698 } } ], "vout": [ { "amount": 536241053267, "target": { "key": "356b8b07fd30d5cd6808ca623635707e1f744e921c57cfb26a955b3a2661e2f4" } } ], "extra": [ 1, 185, 252, 238, 167, 51, 181, 162, 86, 209, 92, 150, 138, 16, 152, 19, 68, 196, 238, 42, 45, 233, 191, 38, 10, 40, 239, 128, 77, 230, 149, 4, 187, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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