Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e417a402c6297c6bf7eb69318cb49c89624ad394e557560cf08ba197373f608f

Tx prefix hash: 91f8079d4cd2f6471c445e8704b8b1545591327e201195e3a925915b8ef8e2a8
Tx public key: 9b7e11653a942e33db1231f323cffc70e8938c3d39bf21a511762bbee3aa45e6
Timestamp: 1734909504 Timestamp [UCT]: 2024-12-22 23:18:24 Age [y:d:h:m:s]: 00:081:19:59:19
Block: 1181074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58253 RingCT/type: yes/0
Extra: 019b7e11653a942e33db1231f323cffc70e8938c3d39bf21a511762bbee3aa45e60211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c80caa094d0fb9f4285cb74f065a9a1ad745576cbc44d5231652585bb88fd20 0.600000000000 1667489 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": 1181084, "vin": [ { "gen": { "height": 1181074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c80caa094d0fb9f4285cb74f065a9a1ad745576cbc44d5231652585bb88fd20" } } ], "extra": [ 1, 155, 126, 17, 101, 58, 148, 46, 51, 219, 18, 49, 243, 35, 207, 252, 112, 232, 147, 140, 61, 57, 191, 33, 165, 17, 118, 43, 190, 227, 170, 69, 230, 2, 17, 0, 0, 0, 5, 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