Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 537cfa72f07f6e6d08e60db8bceda1c6744c3e2fdfb18dedcd17a73fdba533f4

Tx prefix hash: e0d4bca9e11d1c0ec8e0d775fde356d8f741e7f8019d87d9c924bd76270fc866
Tx public key: fbddb22cbabf4bf8d053b2f3c040eb89cb404760e9e92678d7696a35bd995603
Timestamp: 1685014668 Timestamp [UCT]: 2023-05-25 11:37:48 Age [y:d:h:m:s]: 01:239:12:23:31
Block: 767759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432576 RingCT/type: yes/0
Extra: 01fbddb22cbabf4bf8d053b2f3c040eb89cb404760e9e92678d7696a35bd99560302110000000633af99f4000000000000000000

1 output(s) for total of 1.754267826000 dcy

stealth address amount amount idx
00: fd6aecca5f5df62c79610e9c2b9d464df163f156293e6cb8f83769885591421f 1.754267826000 1216898 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": 767769, "vin": [ { "gen": { "height": 767759 } } ], "vout": [ { "amount": 1754267826, "target": { "key": "fd6aecca5f5df62c79610e9c2b9d464df163f156293e6cb8f83769885591421f" } } ], "extra": [ 1, 251, 221, 178, 44, 186, 191, 75, 248, 208, 83, 178, 243, 192, 64, 235, 137, 203, 64, 71, 96, 233, 233, 38, 120, 215, 105, 106, 53, 189, 153, 86, 3, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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