Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a4974fbde6fc91a2798a1744b9b8c0ebaaafa3fd5f9fa6c6bbfab5715ae7175

Tx prefix hash: aae529938b47e892a310e745d327be421d6fff3d7fe0afade100172e0e8a3778
Tx public key: 07671b092191ddd6dc5c1f14453630e973c78ebb0cf5b2260e02313680964c56
Timestamp: 1737334156 Timestamp [UCT]: 2025-01-20 00:49:16 Age [y:d:h:m:s]: 00:149:23:28:05
Block: 1201066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106931 RingCT/type: yes/0
Extra: 0107671b092191ddd6dc5c1f14453630e973c78ebb0cf5b2260e02313680964c56021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06759a49dc450231b1b8b99f168f9986d8398f3fcc94f502cb13102f9df9663f 0.600000000000 1687715 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": 1201076, "vin": [ { "gen": { "height": 1201066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06759a49dc450231b1b8b99f168f9986d8398f3fcc94f502cb13102f9df9663f" } } ], "extra": [ 1, 7, 103, 27, 9, 33, 145, 221, 214, 220, 92, 31, 20, 69, 54, 48, 233, 115, 199, 142, 187, 12, 245, 178, 38, 14, 2, 49, 54, 128, 150, 76, 86, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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