Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e27ff8afe9d258cc31288c49f475bcaecffccd52e9a0b2756d5a8ca20df4ff2b

Tx prefix hash: 1a31f2c37393f38dd833209f127d980f9b1f17424ad54ce1a0cf0a37a610c1d9
Tx public key: af500ab1f03f9aa496a4e38d869877266d0c0380ab37864421be7dc2db92980f
Timestamp: 1726567094 Timestamp [UCT]: 2024-09-17 09:58:14 Age [y:d:h:m:s]: 00:223:16:21:45
Block: 1111995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159723 RingCT/type: yes/0
Extra: 01af500ab1f03f9aa496a4e38d869877266d0c0380ab37864421be7dc2db92980f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 543fd20a73a584a685392fcf111d0f5514f7d050c7d9c775d258be7a0e05d129 0.600000000000 1591152 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": 1112005, "vin": [ { "gen": { "height": 1111995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "543fd20a73a584a685392fcf111d0f5514f7d050c7d9c775d258be7a0e05d129" } } ], "extra": [ 1, 175, 80, 10, 177, 240, 63, 154, 164, 150, 164, 227, 141, 134, 152, 119, 38, 109, 12, 3, 128, 171, 55, 134, 68, 33, 190, 125, 194, 219, 146, 152, 15, 2, 17, 0, 0, 0, 4, 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