Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 444b8e49a437db98f2bb914db7bfca1b9c0ad04ed41db58096e53fa0432f7e5d

Tx prefix hash: da14b1127a132a6dae651ae72f8bea4d41f010981ddf9cb2d804550f6a376c72
Tx public key: 37d7ecae43deebd55bbe2815aef86745348e5c62c46f596b5c9e244c78f1725f
Timestamp: 1734067381 Timestamp [UCT]: 2024-12-13 05:23:01 Age [y:d:h:m:s]: 00:186:05:36:16
Block: 1174095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132813 RingCT/type: yes/0
Extra: 0137d7ecae43deebd55bbe2815aef86745348e5c62c46f596b5c9e244c78f1725f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20e96f1c6b62f3e17a95e575ba4b179ee78b7adf9cdb78015e339c2f4ae58442 0.600000000000 1660202 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": 1174105, "vin": [ { "gen": { "height": 1174095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20e96f1c6b62f3e17a95e575ba4b179ee78b7adf9cdb78015e339c2f4ae58442" } } ], "extra": [ 1, 55, 215, 236, 174, 67, 222, 235, 213, 91, 190, 40, 21, 174, 248, 103, 69, 52, 142, 92, 98, 196, 111, 89, 107, 92, 158, 36, 76, 120, 241, 114, 95, 2, 17, 0, 0, 0, 2, 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