Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41c4995ea3deea6bdb0b4d27c50bb289ef813915d7e644c00a1f8eb7b95b3940

Tx prefix hash: 05a4f84a3c31c925a363ee4853c32c615b5d31abf5af3f791c8c5aeeff568da0
Tx public key: 60100fc26f8ce0ad76083e84a609f88d5a10ac7bbb3924d256519ed4c7aca542
Timestamp: 1699354561 Timestamp [UCT]: 2023-11-07 10:56:01 Age [y:d:h:m:s]: 01:025:00:48:27
Block: 886397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279284 RingCT/type: yes/0
Extra: 0160100fc26f8ce0ad76083e84a609f88d5a10ac7bbb3924d256519ed4c7aca54202110000000175e3f0e9000000000000000000

1 output(s) for total of 0.709575777000 dcy

stealth address amount amount idx
00: 2e57e33cf5fab1b573c90ad7011afd21ddc38101a858d33c8b709a1eb93902d8 0.709575777000 1342212 of 0

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": 886407, "vin": [ { "gen": { "height": 886397 } } ], "vout": [ { "amount": 709575777, "target": { "key": "2e57e33cf5fab1b573c90ad7011afd21ddc38101a858d33c8b709a1eb93902d8" } } ], "extra": [ 1, 96, 16, 15, 194, 111, 140, 224, 173, 118, 8, 62, 132, 166, 9, 248, 141, 90, 16, 172, 123, 187, 57, 36, 210, 86, 81, 158, 212, 199, 172, 165, 66, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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