Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 286f410b4efdd85842237068707b1c5edb66a372b7a10f3e6c4d5752859c3e6b

Tx prefix hash: 7ecfbd6eea42172e2781775a1e63e166a58199b1126b9c1cecb3771b9b3bd9cf
Tx public key: e6914b0ce85b34c7c3e82857b36bb90d639086bcf492a85fdf98dd3135c67e12
Timestamp: 1727585624 Timestamp [UCT]: 2024-09-29 04:53:44 Age [y:d:h:m:s]: 00:194:14:28:20
Block: 1120446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138895 RingCT/type: yes/0
Extra: 01e6914b0ce85b34c7c3e82857b36bb90d639086bcf492a85fdf98dd3135c67e12021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a1ded59440e82016edd629c4e8f98b7963bcea273152b13f17f6dd28e27e637 0.600000000000 1602365 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": 1120456, "vin": [ { "gen": { "height": 1120446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a1ded59440e82016edd629c4e8f98b7963bcea273152b13f17f6dd28e27e637" } } ], "extra": [ 1, 230, 145, 75, 12, 232, 91, 52, 199, 195, 232, 40, 87, 179, 107, 185, 13, 99, 144, 134, 188, 244, 146, 168, 95, 223, 152, 221, 49, 53, 198, 126, 18, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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