Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3e25ca383c712d4949edb7f3da09b96bfedd9c788e6ba5cfad4b6504c9dc6b3

Tx prefix hash: 9e8c32926526b26184c848ebda02679118479c8e104567a791c5f271f99195e2
Tx public key: c279e341c341f874d79db16fbda6b6094b2f0638db48ce86fe0f1cdc7434e12d
Timestamp: 1719971953 Timestamp [UCT]: 2024-07-03 01:59:13 Age [y:d:h:m:s]: 01:133:17:27:31
Block: 1057319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354111 RingCT/type: yes/0
Extra: 01c279e341c341f874d79db16fbda6b6094b2f0638db48ce86fe0f1cdc7434e12d021100000008ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eac83699764481e7517f7d85610ca06f84d4f0d958cc8f6ed2e505622113c7ca 0.600000000000 1527754 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": 1057329, "vin": [ { "gen": { "height": 1057319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eac83699764481e7517f7d85610ca06f84d4f0d958cc8f6ed2e505622113c7ca" } } ], "extra": [ 1, 194, 121, 227, 65, 195, 65, 248, 116, 215, 157, 177, 111, 189, 166, 182, 9, 75, 47, 6, 56, 219, 72, 206, 134, 254, 15, 28, 220, 116, 52, 225, 45, 2, 17, 0, 0, 0, 8, 221, 211, 219, 145, 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