Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a42ec4baa8eeae74bd45e022395c444bf7cbc35ead021df1aa14e098c1e5422

Tx prefix hash: 0a59e90a57b4ba707174f85d75bceae8c9f4ab52321a7020f025e2b21c450fb5
Tx public key: 365a57d66844f755a71515fd3eeb16f8d68a489edd2548a358c2d779f3617efa
Timestamp: 1705266720 Timestamp [UCT]: 2024-01-14 21:12:00 Age [y:d:h:m:s]: 01:063:09:26:23
Block: 935387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306410 RingCT/type: yes/0
Extra: 01365a57d66844f755a71515fd3eeb16f8d68a489edd2548a358c2d779f3617efa0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbfcd2db8548c7e43425a94e12f852df147912803753c23adc430ca9ecc7d1f3 0.600000000000 1393403 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": 935397, "vin": [ { "gen": { "height": 935387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbfcd2db8548c7e43425a94e12f852df147912803753c23adc430ca9ecc7d1f3" } } ], "extra": [ 1, 54, 90, 87, 214, 104, 68, 247, 85, 167, 21, 21, 253, 62, 235, 22, 248, 214, 138, 72, 158, 221, 37, 72, 163, 88, 194, 215, 121, 243, 97, 126, 250, 2, 17, 0, 0, 0, 3, 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