Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae469cd775d6495ab62a216f6aabb570f6c3f159ec338a2b9b12cf7f52575849

Tx prefix hash: 42f643440a425c94b6d665f13b7e7618a4049767a8f31c9a0283c0a63061b119
Tx public key: 4b957aadcecee7e3bda8959d7c0a2c9ddcc09cd4d0ede22d5468a93d31c4226b
Timestamp: 1705700855 Timestamp [UCT]: 2024-01-19 21:47:35 Age [y:d:h:m:s]: 01:069:10:36:51
Block: 938977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310735 RingCT/type: yes/0
Extra: 014b957aadcecee7e3bda8959d7c0a2c9ddcc09cd4d0ede22d5468a93d31c4226b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4400be20b4f405938ec1d8b735e10f5ff4cd5928ca1532f47d656eeb6b91ab7d 0.600000000000 1397061 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": 938987, "vin": [ { "gen": { "height": 938977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4400be20b4f405938ec1d8b735e10f5ff4cd5928ca1532f47d656eeb6b91ab7d" } } ], "extra": [ 1, 75, 149, 122, 173, 206, 206, 231, 227, 189, 168, 149, 157, 124, 10, 44, 157, 220, 192, 156, 212, 208, 237, 226, 45, 84, 104, 169, 61, 49, 196, 34, 107, 2, 17, 0, 0, 0, 2, 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