Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54effac55d5b3da6741c57fe00c6131e6e4df985688253dc4bdffa5813f2eb34

Tx prefix hash: c4846ab275a6565d71eb68722df9ab4dd862229ce6180efc41a9b379274ca041
Tx public key: c1621908cdd2a6401db7e564630dfc8d1ea0c5e1bb9843baf7a3cacdf7bbfaa9
Timestamp: 1728455657 Timestamp [UCT]: 2024-10-09 06:34:17 Age [y:d:h:m:s]: 00:092:02:20:39
Block: 1127657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65833 RingCT/type: yes/0
Extra: 01c1621908cdd2a6401db7e564630dfc8d1ea0c5e1bb9843baf7a3cacdf7bbfaa902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32985798d5b31e3282554fb88870c2d24e0ae7cbc41ae1e6243b9316795070ce 0.600000000000 1610464 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": 1127667, "vin": [ { "gen": { "height": 1127657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32985798d5b31e3282554fb88870c2d24e0ae7cbc41ae1e6243b9316795070ce" } } ], "extra": [ 1, 193, 98, 25, 8, 205, 210, 166, 64, 29, 183, 229, 100, 99, 13, 252, 141, 30, 160, 197, 225, 187, 152, 67, 186, 247, 163, 202, 205, 247, 187, 250, 169, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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