Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6185aa1453075841c7acea13706802f4c5119cbd52e817da4b0ce073cd9d36d

Tx prefix hash: 974b88f7e16ab99093d24c8af86c73b8aefc56e80b6dce56c05a72bec4c7c411
Tx public key: 056e648c4eeaf9b92550c8f3c769b51aa1d6efdc5173cf8b15ed40acd54f3f27
Timestamp: 1693295214 Timestamp [UCT]: 2023-08-29 07:46:54 Age [y:d:h:m:s]: 02:130:15:11:45
Block: 836332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 613179 RingCT/type: yes/0
Extra: 01056e648c4eeaf9b92550c8f3c769b51aa1d6efdc5173cf8b15ed40acd54f3f270211000000024b8f5122000000000000000000

1 output(s) for total of 1.039644793000 dcy

stealth address amount amount idx
00: 6fd78ce5783b5c1f319479cdee5a56eeac631018cc0bf27d09b585915cefedc6 1.039644793000 1288914 of 0

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": 836342, "vin": [ { "gen": { "height": 836332 } } ], "vout": [ { "amount": 1039644793, "target": { "key": "6fd78ce5783b5c1f319479cdee5a56eeac631018cc0bf27d09b585915cefedc6" } } ], "extra": [ 1, 5, 110, 100, 140, 78, 234, 249, 185, 37, 80, 200, 243, 199, 105, 181, 26, 161, 214, 239, 220, 81, 115, 207, 139, 21, 237, 64, 172, 213, 79, 63, 39, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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