Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a407e246bf4d2219668fc21667d0fa13484a8b2a2b105ea700b0c45046bec495

Tx prefix hash: 2e0b8ae711c7da9b2d5f24c64b88c1af70fea6c803208b2543e4ad0b25f76d9d
Tx public key: 639f6e1e8c546abaed79cdf47a89b4407469de5d198b254a9c1943e533a3ef96
Timestamp: 1724486715 Timestamp [UCT]: 2024-08-24 08:05:15 Age [y:d:h:m:s]: 00:222:13:00:53
Block: 1094768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158892 RingCT/type: yes/0
Extra: 01639f6e1e8c546abaed79cdf47a89b4407469de5d198b254a9c1943e533a3ef9602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79760095abb6d8cce1d2a65aa8381b4df305150800a1111c7f133322441aabb2 0.600000000000 1569887 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": 1094778, "vin": [ { "gen": { "height": 1094768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79760095abb6d8cce1d2a65aa8381b4df305150800a1111c7f133322441aabb2" } } ], "extra": [ 1, 99, 159, 110, 30, 140, 84, 106, 186, 237, 121, 205, 244, 122, 137, 180, 64, 116, 105, 222, 93, 25, 139, 37, 74, 156, 25, 67, 229, 51, 163, 239, 150, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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