Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84dc12887b43ed2560e05bfe92f7880d72d272d0597fbc8ecf98d88699590604

Tx prefix hash: 7b09a9c0d950feb1044eee277a4e276845e5b2b2a7de39f29549aeac67cda33c
Tx public key: 0de0ec00272290941543e1ffdcdb134c769840821b2cb2eb4e8c40f520251eb8
Timestamp: 1730910021 Timestamp [UCT]: 2024-11-06 16:20:21 Age [y:d:h:m:s]: 00:155:11:28:31
Block: 1147920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110954 RingCT/type: yes/0
Extra: 010de0ec00272290941543e1ffdcdb134c769840821b2cb2eb4e8c40f520251eb8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e341a549fb0a95f2e0e0861e4fcaf8db9f8bda9d7d8795c2e3215588271dd7a7 0.600000000000 1632633 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": 1147930, "vin": [ { "gen": { "height": 1147920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e341a549fb0a95f2e0e0861e4fcaf8db9f8bda9d7d8795c2e3215588271dd7a7" } } ], "extra": [ 1, 13, 224, 236, 0, 39, 34, 144, 148, 21, 67, 225, 255, 220, 219, 19, 76, 118, 152, 64, 130, 27, 44, 178, 235, 78, 140, 64, 245, 32, 37, 30, 184, 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