Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd8354834e8283fe6f0f6593e0706b3313ebc0fef5f3385d08ac5238e46ff849

Tx prefix hash: a33884cc211b1c9d94d876ecaf9319aa244e35aa73fb039fcedc65473e6623e5
Tx public key: c5b1abcdc77f1c223b9986421c39213e1cffcdee346505f1edc1a5629e1f44dd
Timestamp: 1716197524 Timestamp [UCT]: 2024-05-20 09:32:04 Age [y:d:h:m:s]: 00:329:11:59:19
Block: 1026029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235519 RingCT/type: yes/0
Extra: 01c5b1abcdc77f1c223b9986421c39213e1cffcdee346505f1edc1a5629e1f44dd02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbd00bc7ab8ab9f7623a61f12c61e5dd3fe5577b06de72503fe7374a9206df04 0.600000000000 1492890 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": 1026039, "vin": [ { "gen": { "height": 1026029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbd00bc7ab8ab9f7623a61f12c61e5dd3fe5577b06de72503fe7374a9206df04" } } ], "extra": [ 1, 197, 177, 171, 205, 199, 127, 28, 34, 59, 153, 134, 66, 28, 57, 33, 62, 28, 255, 205, 238, 52, 101, 5, 241, 237, 193, 165, 98, 158, 31, 68, 221, 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