Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22ef6806c8b55c36613a8baf224fb84c33c17d529931ea6ef25151f4c9a46198

Tx prefix hash: f55694393d785a81ee4c6e36b7e910a7126382d43d0a3c68e3d7af5845ecb953
Tx public key: bb94dd65149f7f9686f59d4c0fcbea7aa178ed2191f348d335d5e8dda97a74d1
Timestamp: 1736894838 Timestamp [UCT]: 2025-01-14 22:47:18 Age [y:d:h:m:s]: 00:155:13:10:26
Block: 1197471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110858 RingCT/type: yes/0
Extra: 01bb94dd65149f7f9686f59d4c0fcbea7aa178ed2191f348d335d5e8dda97a74d10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4fec7fc6d10eafb48d888a7d42ed61244978eceb75f1bed2594d8c97483e2c1 0.600000000000 1684080 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": 1197481, "vin": [ { "gen": { "height": 1197471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4fec7fc6d10eafb48d888a7d42ed61244978eceb75f1bed2594d8c97483e2c1" } } ], "extra": [ 1, 187, 148, 221, 101, 20, 159, 127, 150, 134, 245, 157, 76, 15, 203, 234, 122, 161, 120, 237, 33, 145, 243, 72, 211, 53, 213, 232, 221, 169, 122, 116, 209, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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