Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84f4aa51b112f86e1482098e670b40ccdd24f6953ff7e5b311041ccc927bde06

Tx prefix hash: 1857904d001a05e0daa96079f333e1d2a8b578b4e4ef844f2cfe84d95bf132d2
Tx public key: 7cb07a716fb454c3cc0a1f4623dd0cbeab2bd4b20f4c5f68ee6035305979949c
Timestamp: 1723361688 Timestamp [UCT]: 2024-08-11 07:34:48 Age [y:d:h:m:s]: 00:250:06:02:16
Block: 1085433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178742 RingCT/type: yes/0
Extra: 017cb07a716fb454c3cc0a1f4623dd0cbeab2bd4b20f4c5f68ee6035305979949c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9dbe34930f3ab33c7a03bcc7b44190f4da115f944291f84f57cce0c53a94198 0.600000000000 1560016 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": 1085443, "vin": [ { "gen": { "height": 1085433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9dbe34930f3ab33c7a03bcc7b44190f4da115f944291f84f57cce0c53a94198" } } ], "extra": [ 1, 124, 176, 122, 113, 111, 180, 84, 195, 204, 10, 31, 70, 35, 221, 12, 190, 171, 43, 212, 178, 15, 76, 95, 104, 238, 96, 53, 48, 89, 121, 148, 156, 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