Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e15ed63fe25a2409b87da2cfa6ee0192ca7f4825a3d6b0c6bb59947b96fd7ba

Tx prefix hash: 7e5c40ef3e639fb9c00a311ebb2d084ff9281b102cf6241d6964799a32b0da69
Tx public key: c2c4e056b1412ddb209af09cc6abd67e233f1d80bb8c4643ef2a549ec5f68e62
Timestamp: 1707928619 Timestamp [UCT]: 2024-02-14 16:36:59 Age [y:d:h:m:s]: 01:058:02:36:04
Block: 957465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302585 RingCT/type: yes/0
Extra: 01c2c4e056b1412ddb209af09cc6abd67e233f1d80bb8c4643ef2a549ec5f68e6202110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82508d9323c0ce3376616ca85439e9f934483700c7252a9e8471108d36f52aae 0.600000000000 1416783 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": 957475, "vin": [ { "gen": { "height": 957465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82508d9323c0ce3376616ca85439e9f934483700c7252a9e8471108d36f52aae" } } ], "extra": [ 1, 194, 196, 224, 86, 177, 65, 45, 219, 32, 154, 240, 156, 198, 171, 214, 126, 35, 63, 29, 128, 187, 140, 70, 67, 239, 42, 84, 158, 197, 246, 142, 98, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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