Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58a2104453783afc96acae02844361bbf85780b9b98ae8e50ef4f7449d7d6a0f

Tx prefix hash: ffe93e77438f22aa4f9ec57f5c15391caa63630bde873dd53cf54ddceef066f8
Tx public key: d053e7baee99d2c0c76189433f8ea8e217f2445a9669f9fe28e78a729b5cbf37
Timestamp: 1705476996 Timestamp [UCT]: 2024-01-17 07:36:36 Age [y:d:h:m:s]: 01:297:14:27:51
Block: 937132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471525 RingCT/type: yes/0
Extra: 01d053e7baee99d2c0c76189433f8ea8e217f2445a9669f9fe28e78a729b5cbf370211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 086b6b9224bb1fac216644a1a6adbd72947032d9425faf323b261ed087b7fca8 0.600000000000 1395176 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": 937142, "vin": [ { "gen": { "height": 937132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "086b6b9224bb1fac216644a1a6adbd72947032d9425faf323b261ed087b7fca8" } } ], "extra": [ 1, 208, 83, 231, 186, 238, 153, 210, 192, 199, 97, 137, 67, 63, 142, 168, 226, 23, 242, 68, 90, 150, 105, 249, 254, 40, 231, 138, 114, 155, 92, 191, 55, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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