Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 333428ece1b542e4ecd5fde34f0157b9170932ed962e959b2ede685924becfcc

Tx prefix hash: acfcaa332ebb1e265cda20a5dab3f5851f3b7ba672f0f5fea846d6dad8539a7e
Tx public key: 0ca954bc0ae8f8eeee405eb3248802856cecffd5af3a2ac2a7b3ea55a68bfcb3
Timestamp: 1578223309 Timestamp [UCT]: 2020-01-05 11:21:49 Age [y:d:h:m:s]: 05:060:00:30:39
Block: 39135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1192801 RingCT/type: yes/0
Extra: 010ca954bc0ae8f8eeee405eb3248802856cecffd5af3a2ac2a7b3ea55a68bfcb302110000008abd0f9f9f000000000000000000

1 output(s) for total of 455.342130670000 dcy

stealth address amount amount idx
00: 1d4916c30d3a99a8b4250e19ff9c4b67802867081a4176dca2befe85e7376dc9 455.342130670000 67258 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": 39145, "vin": [ { "gen": { "height": 39135 } } ], "vout": [ { "amount": 455342130670, "target": { "key": "1d4916c30d3a99a8b4250e19ff9c4b67802867081a4176dca2befe85e7376dc9" } } ], "extra": [ 1, 12, 169, 84, 188, 10, 232, 248, 238, 238, 64, 94, 179, 36, 136, 2, 133, 108, 236, 255, 213, 175, 58, 42, 194, 167, 179, 234, 85, 166, 139, 252, 179, 2, 17, 0, 0, 0, 138, 189, 15, 159, 159, 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