Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 923f2d44f940e7f5c5fb16eeb030d1b415d3a7e99edc9a57cda7df012b897c8b

Tx prefix hash: 0de6a4697d4de6211d07399e780acff1034fee7d05a73425ab729ec4b0905a7e
Tx public key: 4cd6f86b1cd57eab975f218b943b1cf40d6824eb7847ad20efa5bae5c4e63252
Timestamp: 1735304514 Timestamp [UCT]: 2024-12-27 13:01:54 Age [y:d:h:m:s]: 00:114:10:51:59
Block: 1184304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81592 RingCT/type: yes/0
Extra: 014cd6f86b1cd57eab975f218b943b1cf40d6824eb7847ad20efa5bae5c4e632520211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a421542f8a5520640b3c0c5e2bb5a882b1c538f121fe73acd7ea94f6ef24db06 0.600000000000 1670761 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": 1184314, "vin": [ { "gen": { "height": 1184304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a421542f8a5520640b3c0c5e2bb5a882b1c538f121fe73acd7ea94f6ef24db06" } } ], "extra": [ 1, 76, 214, 248, 107, 28, 213, 126, 171, 151, 95, 33, 139, 148, 59, 28, 244, 13, 104, 36, 235, 120, 71, 173, 32, 239, 165, 186, 229, 196, 230, 50, 82, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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