Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65c8f3467ef562f668c6ae437803f8ea98b3e32b5af6e291f514fcdb1f5b3d53

Tx prefix hash: cab6c8b5840382cd24e88fd79fd987f769622e7024f34ac40e9923346b5d9094
Tx public key: 1d0ab23f1f74bfd6894f5aabe133a486dcc38f24b55a81b9f67923230c09d664
Timestamp: 1716429136 Timestamp [UCT]: 2024-05-23 01:52:16 Age [y:d:h:m:s]: 00:310:09:38:35
Block: 1027949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221856 RingCT/type: yes/0
Extra: 011d0ab23f1f74bfd6894f5aabe133a486dcc38f24b55a81b9f67923230c09d6640211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce0387460e7a24bdc983000c0ebc30a07fc0263bdb36f074afc36225e9f9d9f7 0.600000000000 1495832 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": 1027959, "vin": [ { "gen": { "height": 1027949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce0387460e7a24bdc983000c0ebc30a07fc0263bdb36f074afc36225e9f9d9f7" } } ], "extra": [ 1, 29, 10, 178, 63, 31, 116, 191, 214, 137, 79, 90, 171, 225, 51, 164, 134, 220, 195, 143, 36, 181, 90, 129, 185, 246, 121, 35, 35, 12, 9, 214, 100, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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