Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2a173dab30e29925ef1716a2fa67c7d9323af17d4d4d1446772083b8759b0f9

Tx prefix hash: efc08f95848a0fae42bce0307b5fdc9413796046ba3aca7fb5a54bb0ac66df9f
Tx public key: 2dab93c5cc3d251b38c25e35c89ecd5bb897e734a98628ca61d6e1314861ed0a
Timestamp: 1725080591 Timestamp [UCT]: 2024-08-31 05:03:11 Age [y:d:h:m:s]: 00:220:07:12:58
Block: 1099676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157290 RingCT/type: yes/0
Extra: 012dab93c5cc3d251b38c25e35c89ecd5bb897e734a98628ca61d6e1314861ed0a02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f5f005f28ef1a3ad9f97216d8f1ae72dc3147c95e0cfd6ca34186aecf01148f 0.600000000000 1575641 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": 1099686, "vin": [ { "gen": { "height": 1099676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f5f005f28ef1a3ad9f97216d8f1ae72dc3147c95e0cfd6ca34186aecf01148f" } } ], "extra": [ 1, 45, 171, 147, 197, 204, 61, 37, 27, 56, 194, 94, 53, 200, 158, 205, 91, 184, 151, 231, 52, 169, 134, 40, 202, 97, 214, 225, 49, 72, 97, 237, 10, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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