Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8ac75d33e870c3664f6ae99b47828d023e8e46eba53606d450e2fdf99db0fe8

Tx prefix hash: 9722f64977b5fba4b156b5cff54ac1338dcc13f4eb48f3d24b4f832cce15669a
Tx public key: 61e7df0a5e7fd66b1e6d3dd4f2ec75174c3533f00c5c91561e341f77e2bfd983
Timestamp: 1669613956 Timestamp [UCT]: 2022-11-28 05:39:16 Age [y:d:h:m:s]: 02:090:08:35:10
Block: 640717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586271 RingCT/type: yes/0
Extra: 0161e7df0a5e7fd66b1e6d3dd4f2ec75174c3533f00c5c91561e341f77e2bfd98302110000000375e3f0e9000000000000000000

1 output(s) for total of 4.624221247000 dcy

stealth address amount amount idx
00: 88d33034299df4020f9984d1f230da5682b8441ffbededa12bb602b81d697718 4.624221247000 1080474 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": 640727, "vin": [ { "gen": { "height": 640717 } } ], "vout": [ { "amount": 4624221247, "target": { "key": "88d33034299df4020f9984d1f230da5682b8441ffbededa12bb602b81d697718" } } ], "extra": [ 1, 97, 231, 223, 10, 94, 127, 214, 107, 30, 109, 61, 212, 242, 236, 117, 23, 76, 53, 51, 240, 12, 92, 145, 86, 30, 52, 31, 119, 226, 191, 217, 131, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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