Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 858d5b23aad94ef9a60944a87cace6814f9d32c0e7feabf480005d2f53d99fcd

Tx prefix hash: 380b6b668c33c7b848360dccd73206dede26e6ae72d9e5cfa7bc6706bb92cc40
Tx public key: d0a6dfcb867edc744d85b616d69513f224b8c16cee580a4d12823b682904b2c8
Timestamp: 1718651394 Timestamp [UCT]: 2024-06-17 19:09:54 Age [y:d:h:m:s]: 00:332:12:09:03
Block: 1046377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237634 RingCT/type: yes/0
Extra: 01d0a6dfcb867edc744d85b616d69513f224b8c16cee580a4d12823b682904b2c802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 663bf56e9488d60f9d62500ed4ae70d808e1e56951db39eb92a4d1afff538e5e 0.600000000000 1516188 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": 1046387, "vin": [ { "gen": { "height": 1046377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "663bf56e9488d60f9d62500ed4ae70d808e1e56951db39eb92a4d1afff538e5e" } } ], "extra": [ 1, 208, 166, 223, 203, 134, 126, 220, 116, 77, 133, 182, 22, 214, 149, 19, 242, 36, 184, 193, 108, 238, 88, 10, 77, 18, 130, 59, 104, 41, 4, 178, 200, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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