Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e87579b8878c3422e3094560151f9d4ddf81c3dbb8f1a8ca18fb779e761a4b9c

Tx prefix hash: a41b131069c1a6282af37d59c1a26205dd930fee4cd89fb54952266cbeea905d
Tx public key: a7ba5f9fc6ee00fa9510c5bbbeca84ef529546e5d34206bd1c13073d95eb5aab
Timestamp: 1733420208 Timestamp [UCT]: 2024-12-05 17:36:48 Age [y:d:h:m:s]: 00:332:22:53:42
Block: 1168716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235461 RingCT/type: yes/0
Extra: 01a7ba5f9fc6ee00fa9510c5bbbeca84ef529546e5d34206bd1c13073d95eb5aab021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b6541dfb27f93e9ea8eee2bd8e0aa792d960e9e9e380c1d111d3634826f9a4e 0.600000000000 1654427 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": 1168726, "vin": [ { "gen": { "height": 1168716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b6541dfb27f93e9ea8eee2bd8e0aa792d960e9e9e380c1d111d3634826f9a4e" } } ], "extra": [ 1, 167, 186, 95, 159, 198, 238, 0, 250, 149, 16, 197, 187, 190, 202, 132, 239, 82, 149, 70, 229, 211, 66, 6, 189, 28, 19, 7, 61, 149, 235, 90, 171, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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