Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b35c77f212657fe9ed19cec973093159687cfa2b0a0829ff14b1e9e8173aff0

Tx prefix hash: 30aff4c4e9c41d3c7704390b27043b105a1c9ae305089da7a451e8eabc3903d8
Tx public key: f69094204a18d4b04e80a90b976f9b4f468ee9c611862c54026a138471411ac5
Timestamp: 1712177866 Timestamp [UCT]: 2024-04-03 20:57:46 Age [y:d:h:m:s]: 01:051:14:38:35
Block: 992673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297913 RingCT/type: yes/0
Extra: 01f69094204a18d4b04e80a90b976f9b4f468ee9c611862c54026a138471411ac502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de5a2fa0fb262403d77c2176eb222784b534a95e69a6b7f198a3bc7854b1ddea 0.600000000000 1453047 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": 992683, "vin": [ { "gen": { "height": 992673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de5a2fa0fb262403d77c2176eb222784b534a95e69a6b7f198a3bc7854b1ddea" } } ], "extra": [ 1, 246, 144, 148, 32, 74, 24, 212, 176, 78, 128, 169, 11, 151, 111, 155, 79, 70, 142, 233, 198, 17, 134, 44, 84, 2, 106, 19, 132, 113, 65, 26, 197, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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