Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8ef8ce06cff17bc2c8b8976dd21b02f018c08636c9528935d9c2bf631edb76d

Tx prefix hash: 48a39965db30afc515ee002a1f72053ae0f2e71090374de0ae616acfa9d55ece
Tx public key: 4cb12ac0c8ef43dfcd36ff9a79c131b03968406a84d5e69a15dff7d6d96bdb67
Timestamp: 1727313716 Timestamp [UCT]: 2024-09-26 01:21:56 Age [y:d:h:m:s]: 00:059:17:17:59
Block: 1118189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42680 RingCT/type: yes/0
Extra: 014cb12ac0c8ef43dfcd36ff9a79c131b03968406a84d5e69a15dff7d6d96bdb67021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b944d1ac8dfa83c2ac5c842ed53b2a9bec0a8cda0799c837fd697006b6fa000c 0.600000000000 1599296 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": 1118199, "vin": [ { "gen": { "height": 1118189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b944d1ac8dfa83c2ac5c842ed53b2a9bec0a8cda0799c837fd697006b6fa000c" } } ], "extra": [ 1, 76, 177, 42, 192, 200, 239, 67, 223, 205, 54, 255, 154, 121, 193, 49, 176, 57, 104, 64, 106, 132, 213, 230, 154, 21, 223, 247, 214, 217, 107, 219, 103, 2, 17, 0, 0, 0, 2, 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