Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3292c3254edfb7d7fb2d8c021dba927f070727b1f2d6540df8f55f7f369d5e8

Tx prefix hash: e7978ebe7b0fbc850a3f980fed7a9bde0c474123882c66a5fc0637e06d6fde6f
Tx public key: aee8e461172590e822487db0d294d173e737f1b6688526863fe1c6ecb34861e0
Timestamp: 1734664691 Timestamp [UCT]: 2024-12-20 03:18:11 Age [y:d:h:m:s]: 00:110:10:59:20
Block: 1179045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78708 RingCT/type: yes/0
Extra: 01aee8e461172590e822487db0d294d173e737f1b6688526863fe1c6ecb34861e0021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bbb25efc1ca63e64f69c693cd2c71f8e4f11b737fb63c93f83a497629cd908a 0.600000000000 1665436 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": 1179055, "vin": [ { "gen": { "height": 1179045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bbb25efc1ca63e64f69c693cd2c71f8e4f11b737fb63c93f83a497629cd908a" } } ], "extra": [ 1, 174, 232, 228, 97, 23, 37, 144, 232, 34, 72, 125, 176, 210, 148, 209, 115, 231, 55, 241, 182, 104, 133, 38, 134, 63, 225, 198, 236, 179, 72, 97, 224, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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