Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b76a371a91c8588055054e5dfd813c3669356cf3203546a6d46fc80a85dea449

Tx prefix hash: 178fdbb7a9f86757ef2671507ed3204a9955bc7f1b9bd5ad3ed8356fd56a15a9
Tx public key: 5dcd9ac45b9e3128199007912fb8a7a1b4915922aa484a9d1c184e0996a07f66
Timestamp: 1715232902 Timestamp [UCT]: 2024-05-09 05:35:02 Age [y:d:h:m:s]: 00:245:23:45:28
Block: 1018037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176062 RingCT/type: yes/0
Extra: 015dcd9ac45b9e3128199007912fb8a7a1b4915922aa484a9d1c184e0996a07f6602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45d190e807ca9a554b4958e4c227eb572e55a2ec96d17d1160e20eb9d044e6e3 0.600000000000 1481822 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": 1018047, "vin": [ { "gen": { "height": 1018037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45d190e807ca9a554b4958e4c227eb572e55a2ec96d17d1160e20eb9d044e6e3" } } ], "extra": [ 1, 93, 205, 154, 196, 91, 158, 49, 40, 25, 144, 7, 145, 47, 184, 167, 161, 180, 145, 89, 34, 170, 72, 74, 157, 28, 24, 78, 9, 150, 160, 127, 102, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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