Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4f847372934d8fcb604856d91f5711b6adf0a84eaf0aded138028d97d96cce5

Tx prefix hash: c7a6c09e3a1c61939501a49b1e4a28e88226690b9468b98b7d69ec8c393c44e1
Tx public key: 463f1546466e37bb326ce20cb511e8099b77ad73c126a603d52a8f0478e417f6
Timestamp: 1712782479 Timestamp [UCT]: 2024-04-10 20:54:39 Age [y:d:h:m:s]: 01:026:01:14:37
Block: 997698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279601 RingCT/type: yes/0
Extra: 01463f1546466e37bb326ce20cb511e8099b77ad73c126a603d52a8f0478e417f60211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9edd8910c88e6eccfa6d0a171502a23767a477a92ec739e0760a69e0c103e6dd 0.600000000000 1458132 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": 997708, "vin": [ { "gen": { "height": 997698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9edd8910c88e6eccfa6d0a171502a23767a477a92ec739e0760a69e0c103e6dd" } } ], "extra": [ 1, 70, 63, 21, 70, 70, 110, 55, 187, 50, 108, 226, 12, 181, 17, 232, 9, 155, 119, 173, 115, 193, 38, 166, 3, 213, 42, 143, 4, 120, 228, 23, 246, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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