Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75dcabf1fe44a63f5d8177223c6ff498bb6c51440fd609a2be8704be5a7bece0

Tx prefix hash: b3c58950c1115e6c5858dd59c444216b40ff1bccd2d30d5b65eeffa6f2175d5e
Tx public key: 737e9f64f597d612df382caac3d78be3c53e8afaa991cddd695e53cc065f66c0
Timestamp: 1725396649 Timestamp [UCT]: 2024-09-03 20:50:49 Age [y:d:h:m:s]: 00:119:15:51:24
Block: 1102298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85580 RingCT/type: yes/0
Extra: 01737e9f64f597d612df382caac3d78be3c53e8afaa991cddd695e53cc065f66c002110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fd606d5eea7502d2a8cda1c318ef1654bfcf7da84fa32bbceed231425752eb2 0.600000000000 1578681 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": 1102308, "vin": [ { "gen": { "height": 1102298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fd606d5eea7502d2a8cda1c318ef1654bfcf7da84fa32bbceed231425752eb2" } } ], "extra": [ 1, 115, 126, 159, 100, 245, 151, 214, 18, 223, 56, 44, 170, 195, 215, 139, 227, 197, 62, 138, 250, 169, 145, 205, 221, 105, 94, 83, 204, 6, 95, 102, 192, 2, 17, 0, 0, 0, 13, 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